System and method for storage discovery in a storage area network using device domains under control of a storage device

ABSTRACT

A storage device coupled to a fabric includes a memory and a processor operable to receive, default domain information for a storage area network (SAN) from a management server coupled to the fabric. The default domain information including a list of host systems and a list of initiators on the SAN. The processor also sends the default domain information to a management station to configure a discovery domain including a host system selected from the list of host systems and an initiator selected from the list of initiators, receives the discovery domain from the management station, directs the management server to add the first discovery domain to a list of device domains implemented by the management server on the SAN, and directs the management server to enable the first discovery domain.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/286,627, entitled “System and Method for Storage Discovery in aStorage Area Network Using Device Domains Under Control of a StorageDevice”, now U.S. Pat. No. 8,352,586, filed on Nov. 1, 2011, which is acontinuation of U.S. patent application Ser. No. 12/582,269, filed onOct. 20, 2009, now U.S. Pat. No. 8,073,942, the disclosures of which arehereby expressly incorporated by reference in their entirety.

FIELD OF THE DISCLOSURE

This disclosure relates generally to information handling systems, andrelates more particularly to a storage area network in an informationhandling system.

BACKGROUND

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option is an information handling system. An information handlingsystem generally processes, compiles, stores, or communicatesinformation or data for business, personal, or other purposes. Becausetechnology and information handling needs and requirements can varybetween different applications, information handling systems can alsovary regarding what information is handled, how the information ishandled, how much information is processed, stored, or communicated, andhow quickly and efficiently the information can be processed, stored, orcommunicated. The variations in information handling systems allowinformation handling systems to be general or configured for a specificuser or specific use such as financial transaction processing, airlinereservations, enterprise data storage, or global communications. Inaddition, information handling systems can include a variety of hardwareand software resources that can be configured to process, store, andcommunicate information and can include one or more computer systems,data storage systems, and networking systems. An information handlingsystem can include a storage area network that includes a mechanism toset up and control the storage resources that are accessible to theinformation handling system.

BRIEF DESCRIPTION OF THE DRAWINGS

It will be appreciated that for simplicity and clarity of illustration,elements illustrated in the Figures have not necessarily been drawn toscale. For example, the dimensions of some of the elements areexaggerated relative to other elements. Embodiments incorporatingteachings of the present disclosure are illustrated and described withrespect to the drawings presented herein, in which:

FIG. 1 is a block diagram illustrating an information handling systemwith a storage area network, according to an embodiment of the presentdisclosure

FIG. 2 is a block diagram illustrating an information handling systemsimilar to FIG. 1, and a method of establishing device domains thereon;

FIG. 3 is a block diagram illustrating the information handling systemof FIG. 2, and a method of changing device domains thereon; and

FIG. 4 is a functional block diagram illustrating an exemplaryembodiment of an information handling system.

The use of the same reference symbols in different drawings indicatessimilar or identical items.

DETAILED DESCRIPTION OF DRAWINGS

The following description in combination with the Figures is provided toassist in understanding the teachings disclosed herein. The followingdiscussion will focus on specific implementations and embodiments of theteachings. This focus is provided to assist in describing the teachings,and should not be interpreted as a limitation on the scope orapplicability of the teachings. However, other teachings can be used inthis application. The teachings can also be used in other applications,and with several different types of architectures, such as distributedcomputing architectures, client/server architectures, or middlewareserver architectures and associated resources.

For purposes of this disclosure, an information handling system caninclude any instrumentality or aggregate of instrumentalities operableto compute, classify, process, transmit, receive, retrieve, originate,switch, store, display, manifest, detect, record, reproduce, handle, oruse any form of information, intelligence, or data for business,scientific, control, entertainment, or other purposes. For example, aninformation handling system can be a personal computer, a PDA, aconsumer electronic device, a network server or storage device, a switchrouter, wireless router, or other network communication device, or anyother suitable device and can vary in size, shape, performance,functionality, and price. The information handling system can includememory (volatile such as random-access memory), nonvolatile such asread-only memory or flash memory) or any combination thereof), one ormore processing resources, such as a central processing unit (CPU), agraphics processing unit (GPU), hardware or software control logic, orany combination thereof. Additional components of the informationhandling system can include one or more storage devices, one or morecommunications ports for communicating with external devices, as well asvarious input and output (I/O) devices such as a keyboard, a mouse, avideo/graphic display, or any combination thereof. The informationhandling system can also include one or more buses operable to transmitcommunications between the various hardware components. Portions of aninformation handling system may themselves be considered informationhandling systems.

Portions of an information handling system, when referred to as a“device,” a “module,” or the like, can be configured as hardware,software (which can include firmware), or any combination thereof. Forexample, a portion of an information handling system device may behardware such as, for example, an integrated circuit (such as anApplication Specific Integrated Circuit (ASIC), a Field ProgrammableGate Array (FPGA), a structured ASIC, or a device embedded on a largerchip), a card (such as a Peripheral Component Interface (PCI) card, aPCI-express card, a Personal Computer Memory Card InternationalAssociation (PCMCIA) card, or other such expansion card), or a system(such as a motherboard, a system-on-a-chip (SoC), or a stand-alonedevice). Similarly, the device could be software, including firmwareembedded at a device, such as a Pentium class or PowerPC™ brandprocessor, or other such device, or software capable of operating arelevant environment of the information handling system. The devicecould also be a combination of any of the foregoing examples of hardwareor software. Note that an information handling system can include anintegrated circuit or a board-level product having portions thereof thatcan also be any combination of hardware and software.

Devices or programs that are in communication with one another need notbe in continuous communication with each other unless expresslyspecified otherwise. In addition, devices or programs that are incommunication with one another may communicate directly or indirectlythrough one or more intermediaries.

An information handling system can include one or more host processingsystems, and a storage system that are connected to a common network ordata storage fabric. The data storage system can include a storagemanagement server and one or more storage devices. In order to ensuresecure access to data, and to avoid data corruption, the data storagesystem can provide a mechanism to create and maintain device domainsthat limit the access of a particular host processing system to a subsetof the storage devices. In a particular embodiment, described herein,the storage devices include a management station that creates andmaintains the device domains on the storage management server, therebyreducing the amount of management activity needed to maintain theinformation handling system.

FIG. 1 illustrates an information handling system 100 according to anembodiment of the present disclosure, including host processing system110, one or more additional host processing systems 115, and a storagearea network (SAN) 150. SAN 150 includes a storage management server120, a fabric 130, and one or more logical storage devices representedby storage devices 142, 144, and 146, and labeled LUN-1, LUN-2, andLUN-3, respectively. Host processing systems 110 includes host busadapters (HBAs) 112 and 114 labeled HBA-1 and HBA-2, respectively, andhost processing systems 115 includes host bus adapter 117 labeled HBA-3.Host processing system 110 is connected to fabric 130 through HBAs 112and 114, and host processing system 115 is connected to fabric 130through HBA 117. HBAs 112 and 114 are adapted to transfer data betweenhost processing system 110 and fabric 130, and host bus adapter 117 isadapted to transfer data between host processing system 115 and fabric130 according to a particular protocol associated with fabric 130. Anon-limiting example of fabric 130 includes a Small Computer SystemInterface (SCSI) fabric, a Fibre Channel (FC) fabric, an Internet SCSI(iSCSI) fabric, another data fabric or any combination thereof. Storagemanagement server 120 and storage devices 142, 144, and 146 areconnected to fabric 130. A non-limiting example of storage devices 142,144, and 146 includes a logical unit that may be a disk drive, a drivearray, a virtual disk, a logical partition of a disk drive, anotherstorage medium, or any combination thereof.

In operation, host processing systems 110 and 115 store data on aselected one or more of storage devices 142, 144, and 146. In gainingaccess to a particular storage device 142, 144, or 146, HBAs 112, 114,and 117 will establish a storage session with the particular storagedevice 142, 144, or 146 through a log-in process. When a particularstorage device 142, 144, or 146 is connected to fabric 130, theparticular storage device 142, 144, or 146 is configured with log-incredentials that limit access to the storage capabilities of theparticular storage device 142, 144, or 146. For example, storage devices142, 144, and 146 can be configured with an identifier associated withone or more particular HBA 112, 114, and 117. Then, when an HBA 112,114, or 117 with the proper identifier attempts to log-in to aparticular storage device 142, 144, or 146, the storage device 142, 144,or 146 permits that HBA access. When an HBA 112, 114, or 117 without theproper identifier attempts to log-in to a particular storage device 142,144, or 146, the storage device 142, 144, or 146 denies that HBA access.Note that each storage device 142, 144, and 146 has to be configuredbefore a particular HBA 112, 114, or 117 can access the storagecapabilities of storage devices 142, 144, and 146. Typically,configuration of a storage device in a SAN is done when the storagedevice is added to the SAN, or when the configuration propertieschanges.

In a particular embodiment, on startup, host processing systems 110 and115 discover that storage devices 142, 144, and 146 are connected tofabric 130, and each of HBAs 112, 114, and 117 attempt to automaticallylog-in to each of storage devices 142, 144, and 146. Storage devices142, 144, and 146 either accept or reject the log-in attempts by HBAs112, 114, and 117, based upon the associated log-in credentials. In atypical information handling system, the number of storage devices canbe smaller than the number of host processing systems, and the hostprocessing systems can have more than one HBA. Thus the individuallog-in attempts by the large number of HBAs can constitute a significantload on the storage devices in an information handling system. Inanother embodiment, when host processing systems 110 or 115 is added toinformation handling system 100, an administrator (not illustrated)manually configures the associated HBAs 112 and 114, or 117 to log in toan associated storage device 142, 144, or 146. In this way, the numberof log-in attempts experienced by storage devices 142, 144, and 146 isreduced. However, in this embodiment, when a storage device 142, 144, or146 is added to information handling system 100, the administrator willmanually reconfigure an associated HBA 112, 114, or 117 with thenecessary log-in credentials.

In another embodiment, on startup, host processing systems 110 and 115discover storage management server 120. Storage management server 120includes a management system 122 that creates and maintains one or moredevice domain 124, 126, and 128. Device domains 124, 126, and 128 definethe access relationships among HBAs 112, 114, and 117, and storagedevices 142, 144, and 146. When a particular HBA 112, 114, or 117discovers management server 120, management system 120 sends a list ofthe storage devices 142, 144, or 146 that are included in a particulardevice domain 124, 126, or 128 that also includes the particular HBA112, 114, or 117. The particular HBA 112, 114, or 117 then attempts tolog-in to storage devices 142, 144, or 146 that are included in thelist. The particular HBA 112, 114, or 117 makes no attempt to log-in tostorage devices 142, 144, or 146 that are not included in the list. Anon-limiting example of a device domain includes an iSCSI device domain,a Fibre Channel zone, another domain defining access relationships, or acombination thereof.

For example, as shown in Table 1, a first device domain labeled DD-1 canbe set up to provide storage for a Windows-NT application serverenvironment, where HBA 112 can be associated with a virtual machine thatis running Windows-NT on host processing system 110. Host processingsystem 115 can also be running Windows-NT, and storage device 142 can beformatted with a Windows-NT compatible format. A second device domainlabeled DD-2 can be set up to provide storage for a Linux serverenvironment, where HBA 114 can be associated with a virtual machine thatis running Linux on host processing system 110, and storage device 144can be formatted with a Linux compatible format. A third device domainlabeled DD-3 can be set up to provide back-up and archive storage forthe Windows-NT application server environment, where host processingsystem 115 can function as the back-up server with access to storagedevices 142 and 164. Storage device 164 can also be formatted with aWindows-NT compatible format.

TABLE 1 Device Domains Device Domain Domain Purpose Host Bus AdapterStorage Devices DD-1 NT - App Server HBA-1, HBA-3 LUN-1 DD-2 LinuxServer HBA-2 LUN-2 DD-3 NT - Backup Server HBA-3 LUN-1, LUN-3

Thus, for example, when host processing system 115 is running aWindows-NT back-up application, HBA-3 attaches to fabric 130 anddiscovers storage management server 120. Server manager 122 determinesthat HBA 117 is associated with device domains 124 and 128. Servermanager 122 sends the list of included storage devices 142 and 146 toHBA 117, and HBA 117 attempts to log-in to only storage devices 142 and146. Thus a storage management server functions to reduce the log-inload on the storage devices in an information handling system andprovide logical isolation of devices in the storage fabric. In aparticular embodiment, device domains 124, 126, and 128 are created andconfigured by the administrator using a management station (notillustrated) that is associated with storage management server 120.

FIG. 2 illustrates an information handling system 200 similar toinformation handling system 100, and a method of establishing devicedomains thereon. Information handling system 200 includes one or morehosts 210, and a SAN 270. SAN 270 includes an Internet Storage NameService (iSNS) server 220, an iSCSI fabric 230, one or more storagesystems 240, and a management station 250. Host 210 is similar to hostprocessing systems 110 and 115, and includes an iSNS client 212. iSNSclient 212 can be integrated into HBA 112, 114, or 117, or can beimplemented as a software layer associated with such an HBA. In aparticular example, iSNS client 212 can be associated with a particularHBA 112, 114, or 117, such that each HBA 112, 114, and 117 includes aniSNS client, or iSNS client can be associated with a particular host 110or 115 such that each host 110 and 115 includes an iSNS client, or acombination thereof.

iSNS server 220 is similar to storage management server 120, andincludes a default domain 222 and one or more discovery domains (DD)224. In a particular embodiment, DD 224 describes a discovery domainthat includes at least host 210 and storage system 240. iSCSI fabric 230is similar to fabric 130. Storage system 240 is similar to storagedevices 142, 144, and 146, and includes an iSNS client 240. iSNS client240 is functionally capable of operating as a control node for iSNSserver 220. Host 210, iSNS server 220, and storage system 240 areconnected to iSCSI fabric 230. Management station 250 is connected tostorage system 240. Management station 250 operates to manage thestorage functions of storage system 240, and is accessible to anadministrator (not illustrated) to configure and maintain storage system240. In an embodiment (not illustrated), management station 250 isincluded as a part of storage system 240.

In a particular embodiment, host 210 stores data on storage system 240.When storage system 240 is connected to iSCSI fabric 230, iSNS client242 discovers iSNS server 220 that in turn registers the presence ofstorage system 240. When host 210 is connected to iSCSI fabric 230, iSNSclient 212 discovers iSNS server 220 that in turn registers the presenceof host 210 by adding host 210 to default domain 222. When theadministrator uses management station 250 to configure storage system240 to provide access to host 210, DD 224 is created, as describedbelow, and configured to include host 210 and storage system 240.Optionally, the administrator may configure log-in credentials in iSNSclient 212 for storage system 240. iSNS server 220 sends the informationfrom DD 224 to iSNS client 212. Host 210 then logs-in to storage system240, and the storage capabilities of storage system 240 are thenavailable to host 210.

A method is illustrated with the bold process lines in FIG. 2, where DD224 is created and configured by the administrator using managementstation 250. iSNS client 242 sends a query 261 to iSNS server 220 forthe list of hosts in default domain 222. iSNS server 220 sends aresponse 262 to iSNS client 242 with the requested information. Storagesystem 240 sends the information 263 including the list of hosts indefault domain 222 received by iSNS client 242 to management station250. iSNS client 242 and storage system 240 are configured as a controlnode for iSNS server 220. Thus, when the administrator configuresstorage system 240 to provide host 210 access to the storage resourcesof storage system 240, storage system 240 updates access controlmechanisms to provide access to host 210 and determines a configurationfor DD 222. The configuration includes host 210, and can also includeone or more additional devices including other host processing systems,HBAs, ports, other devices configured as iSCSI initiators on iSCSIfabric 230, or any combination thereof. Storage system 240 then directsiSNS client 242 to send a command 264 to iSNS server 220 to create DD224 that includes storage system 240 and host 210, along with iSCSIinitiator information for the iSCSI initiators (not illustrated)associated with host 210. In addition to creating DD 224, command 264directs iSNS server 220 to enable DD 224.

In response, iSNS server 220 exchanges information 265 with client 212.Information 265 includes a state change notification (SCN) from iSNSserver 220 that informs iSNS client 212 and the iSCSI initiatorsassociated with host 210 about the change in iSCSI fabric 230. Further,information 265 includes a query from iSNS client 212 about the statechange. In addition, information 265 includes a response from iSNSserver 220, informing iSNS client 212 and the iSCSI initiatorsassociated with host 210 of the presence of storage system 240 in DD224. The iSCSI initiators associated with host 210 are configured toautomatically log-in to all storage devices in DD 224, as identified inthe response. Thus, because storage system 240 is included in DD 224,the iSCSI initiators log-in 266 to storage system 240 as describedabove. Other iSCSI initiators that are not included in DD 224 are notinformed of the presence of storage system 240, and do not attempt tolog-in to storage system 240.

FIG. 3 illustrates information handling system 200, and a method ofchanging device domains thereon. Here, iSNS server 220 includes one ormore additional DDs 226. DDs 224 and 226 can be added or changed inresponse to changing conditions on SAN 270. For example, when a logicalstorage device (not illustrated) that is associated with iSNS client 212on another storage device (not illustrated) is moved to storage system240, DD 226 can be created as described above to associate the logicalstorage device on iSNS client 242 with iSNS client 212 on host 210. Inanother example, when the address of storage system 240 is changed onSAN 270, or improved load balancing between host 210 and storage system240 is desired, then, in one embodiment, DD 226 is created as describedabove to associate the new address, or additional ports of storagesystem 240 with iSNS client 212 on host 210, rendering DD 224 redundant.DD 224 can thus be deleted from iSNS server 220. In another embodiment,when the address of storage system 240 is changed on SAN 270, orimproved load balancing between host 210 and storage system 240 isdesired, then the associations in DD 224 are modified as describedbelow.

A method of changing associations is illustrated with the bold processlines in FIG. 3, where DD 224 is modified by the administrator usingmanagement station 250, in response to a change in SAN 270. Anadministrator determines to change the associations in iSNS server 220,and management station 250 sends information 361 with updated DDassociation information to storage system 240. Storage system 240 thendirects iSNS client 242 to send a command 362 to iSNS server 220 tomodify DD 226 to include the updated information associated with storagesystem 240, host 210, and iSCSI initiator information for the iSCSIinitiators (not illustrated) associated with host 210. In addition tomodifying DD 224, command 362 directs iSNS server 220 to re-enable DD224. In response, iSNS server 220 exchanges information 363 with iSNSclient 212. Information 363 includes a state change notification (SCN)from iSNS server 220, a query from iSNS client 212 about the statechange, and a response from iSNS server 220, as described above. Sincestorage system 240 is included in DD 224, the iSCSI initiators log-in364 to storage system 240 as described above. Other iSCSI initiatorsthat are not included in DD 226 are not informed of the presence ofstorage system 240, and do not attempt to log-in to storage system 240.

In a particular embodiment, an information handling system can be usedto carry out one or more of the methods described above. In anotherembodiment, one or more of the systems described above can beimplemented in the form of an information handling system. FIG. 4illustrates a functional block diagram of an embodiment of aninformation handling system, generally designated as 400. Informationhandling system 400 includes processor 410, a chipset 420, a memory 430,a graphics interface 440, an input/output (I/O) interface 450, a diskcontroller 460, a network interface 470, and a disk emulator 480.

Processor 410 is coupled to chipset 420. Chipset 420 supports processor410, allowing processor 410 to process machine-executable code. In aparticular embodiment (not illustrated), information handling system 400includes one or more additional processors, and chipset 420 supports themultiple processors, allowing for simultaneous processing by each of theprocessors, permitting the exchange of information between theprocessors and the other elements of information handling system 400.Processor 410 can be coupled to chipset 420 via a unique channel, or viaa bus that shares information between processor 410, chipset 420, andother elements of information handling system 400.

Memory 430 is coupled to chipset 420. Memory 430 can be coupled tochipset 420 via a unique channel, or via a bus that shares informationbetween chipset 420, memory 430, and other elements of informationhandling system 400. In particular, a bus can share information betweenprocessor 410, chipset 420 and memory 430. In a particular embodiment(not illustrated), processor 410 is coupled to memory 430 through aunique channel. In accordance with another aspect (not illustrated), aninformation handling system can include a separate memory dedicated toeach of the processors. A non-limiting example of memory 430 includesstatic, dynamic. Or non-volatile random access memory (SRAM, DRAM, orNVRAM), read only memory (ROM), flash memory, another type of memory, orany combination thereof.

Graphics interface 440 is coupled to chipset 420. Graphics interface 440can be coupled to chipset 420 via a unique channel, or via a bus thatshares information between chipset 420, graphics interface 440, andother elements of information handling system 400. Graphics interface440 is coupled to a video display 444. Other graphics interfaces (notillustrated) can also be used in addition to graphics interface 440 ifneeded or desired. Video display 444 can include one or more types ofvideo displays, such as a flat panel display or other type of displaydevice.

I/O interface 450 is coupled to chipset 420. I/O interface 450 can becoupled to chipset 420 via a unique channel, or via a bus that sharesinformation between chipset 420, I/O interface 450, and other elementsof information handling system 400. Other I/O interfaces (notillustrated) can also be used in addition to I/O interface 450 if neededor desired. I/O interface 450 is coupled to one or more add-on resources454. Add-on resource 454 can also include another data storage system, agraphics interface, a network interface card (NIC), a sound/videoprocessing card, another suitable add-on resource or any combinationthereof.

Network interface device 470 is coupled to I/O interface 450. Networkinterface 470 can be coupled to I/O interface 450 via a unique channel,or via a bus that shares information between I/O interface 450, networkinterface 470, and other elements of information handling system 400.Other network interfaces (not illustrated) can also be used in additionto network interface 470 if needed or desired. Network interface 470 canbe a network interface card (NIC) disposed within information handlingsystem 400, on a main circuit board (e.g., a baseboard, a motherboard,or any combination thereof), integrated onto another component such aschipset 420, in another suitable location, or any combination thereof.Network interface 470 includes a network channel 472 that provideinterfaces between information handling system 400 and other devices(not illustrated) that are external to information handling system 400.Network interface 470 can also include additional network channels (notillustrated).

Disk controller 460 is coupled to chipset 410. Disk controller 460 canbe coupled to chipset 420 via a unique channel, or via a bus that sharesinformation between chipset 420, disk controller 460, and other elementsof information handling system 400. Other disk controllers (notillustrated) can also be used in addition to disk controller 460 ifneeded or desired. Disk controller 460 can include a disk interface 462.Disk controller 460 can be coupled to one or more disk drives via diskinterface 462. Such disk drives include a hard disk drive (HDD) 464 oran optical disk drive (ODD) 466 (e.g., a Read/Write Compact Disk(R/W-CD), a Read/Write Digital Video Disk (R/W-DVD), a Read/Write miniDigital Video Disk (R/W mini-DVD), or another type of optical diskdrive), or any combination thereof. Additionally, disk controller 460can be coupled to disk emulator 480. Disk emulator 480 can permit asolid-state drive 484 to be coupled to information handling system 400via an external interface. The external interface can include industrystandard busses (e.g., USB or IEEE 1384 (Firewire)) or proprietarybusses, or any combination thereof. Alternatively, solid-state drive 484can be disposed within information handling system 400.

In the embodiments described above, an information handling system caninclude any instrumentality or aggregate of instrumentalities operableto compute, classify, process, transmit, receive, retrieve, originate,switch, store, display, manifest, detect, record, reproduce, handle, oruse any form of information, intelligence, or data for business,scientific, control, entertainment, or other purposes. For example, aninformation handling system can be a personal computer, a PDA, aconsumer electronic device, a network server or storage device, a switchrouter, wireless router, or other network communication device, or anyother suitable device and can vary in size, shape, performance,functionality, and price. The information handling system can includememory (volatile (e.g. random-access memory, etc.), nonvolatile(read-only memory, flash memory etc.) or any combination thereof), oneor more processing resources, such as a central processing unit (CPU), agraphics processing unit (GPU), hardware or software control logic, orany combination thereof. Additional components of the informationhandling system can include one or more storage devices, one or morecommunications ports for communicating with external devices, as wellas, various input and output (I/O) devices, such as a keyboard, a mouse,a video/graphic display, or any combination thereof. The informationhandling system can also include one or more buses operable to transmitcommunications between the various hardware components. Portions of aninformation handling system may themselves be considered informationhandling systems.

When referred to as a “device,” a “module,” or the like, the embodimentsdescribed above can be configured as hardware, software (which caninclude firmware), or any combination thereof. For example, a portion ofan information handling system device may be hardware such as, forexample, an integrated circuit (such as an Application SpecificIntegrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), astructured ASIC, or a device embedded on a larger chip), a card (such asa Peripheral Component Interface (PCI) card, a PCI-express card, aPersonal Computer Memory Card International Association (PCMCIA) card,or other such expansion card), or a system (such as a motherboard, asystem-on-a-chip (SoC), or a stand-alone device). Similarly, the devicecould be software, including firmware embedded at a device, such as aPentium class or PowerPC™ brand processor, or other such device, orsoftware capable of operating a relevant environment of the informationhandling system. The device could also be a combination of any of theforegoing examples of hardware or software. Note that an informationhandling system can include an integrated circuit or a board-levelproduct having portions thereof that can also be any combination ofhardware and software.

Devices, modules, resources, or programs that are in communication withone another need not be in continuous communication with each other,unless expressly specified otherwise. In addition, devices, modules,resources, or programs that are in communication with one another cancommunicate directly or indirectly through one or more intermediaries.

Although only a few exemplary embodiments have been described in detailabove, those skilled in the art will readily appreciate that manymodifications are possible in the exemplary embodiments withoutmaterially departing from the novel teachings and advantages of theembodiments of the present disclosure. Accordingly, all suchmodifications are intended to be included within the scope of theembodiments of the present disclosure as defined in the followingclaims. In the claims, means-plus-function clauses are intended to coverthe structures described herein as performing the recited function andnot only structural equivalents, but also equivalent structures.

What is claimed is:
 1. A storage device coupled to a fabric, the storagedevice comprising: a memory; and a processor operable to: receive, froma management server coupled to the fabric, default domain informationfor a storage area network (SAN), the default domain informationincluding a list of host systems on the SAN, and a list of initiators onthe SAN; send the default domain information to a management station,the management station to configure a first discovery domain including ahost system selected from the list of host systems and an initiatorselected from the list of initiators; receive the first discovery domainfrom the management station; direct the management server to add thefirst discovery domain to a list of device domains implemented by themanagement server on the SAN; and direct the management server to enablethe first discovery domain.
 2. The storage device of claim 1, whereinthe processor is further operable to: send a query to the managementserver for the default domain information for the SAN; wherein receivingthe default domain information from the management server is in responseto sending the query.
 3. The storage device of claim 1, wherein theprocessor is further operable to: receive a log-in request from the hostsystem, the log-in request being initiated by the initiator.
 4. Thestorage device of claim 3, wherein the processor is further operable to:determine that the log-in request is initiated by the initiator; and logthe host system onto the storage device in response to determining thatthe log-in request is initiated by the initiator.
 5. The storage deviceof claim 1, wherein the processor is further operable to: receive asecond discovery domain from the management station; direct themanagement server to add the second discovery domain to the list ofdevice domains; and direct the management server to enable the seconddiscovery domain.
 6. The storage device of claim 5, wherein theprocessor is further operable to: direct the management server to deletethe first device domain from the list of device domains in response toenabling the second discovery domain.
 7. The storage device of claim 1,wherein the fabric comprises an Internet Small Computer System Interfacefabric.
 8. The storage device of claim 1, wherein the storage devicecomprises the management station.
 9. The storage device of claim 1,wherein the storage device includes an Internet Storage Name Service(iSNS) client.
 10. The storage device of claim 1, wherein: themanagement server includes an iSNS server; and the iSNS client is acontrol node for the iSNS server.
 11. A management station comprising: amemory; and a processor operable to: receive, from a storage devicecoupled to the management station, default domain information for astorage area network (SAN), the default domain information including alist of host systems on the SAN, and a list of initiators on the SAN;select a first host system from the list of host systems; select a firstinitiator from the list of initiators; create a first discovery domainfor the SAN; configure the first discovery domain to include the firsthost system and the first initiator; send the first discovery domain tothe storage device; direct the storage device to: send the firstdiscovery domain to a management server of the SAN; direct themanagement server to add the first discovery domain to a list of devicedomains implemented by the management server on the SAN; and direct themanagement server to enable the first discovery domain.
 12. Themanagement station of claim 11, wherein the processor is furtheroperable to: direct the storage device to send a query to the managementserver for the default domain information for the SAN; wherein receivingthe default domain information from the storage device is in response todirecting the storage device to send the query.
 13. The managementstation of claim 11, wherein the processor is further operable to:select a second host system from the list of host systems; select asecond initiator from the list of initiators; create a second discoverydomain for the SAN; and configure the second discovery domain to includethe second host system and the second initiator.
 14. The managementstation of claim 13, wherein the processor is further operable to: sendthe second discovery the storage device; direct the storage device to:send the second discovery domain to the management server; direct themanagement server to add the second discovery domain to the list ofdevice domains; and direct the management server to enable the seconddiscovery domain.
 15. The management station of claim 14, wherein theprocessor is further operable to: direct the storage device to directthe management server to delete the first device domain from the list ofdevice domains in response to enabling the second discovery domain. 16.The management station of claim 11, wherein the management stationcomprises the storage device.
 17. A method comprising: receiving, at astorage device coupled to a fabric, default domain information from amanagement server for a storage area network (SAN), the default domaininformation including a list of host systems on the SAN, and a list ofinitiators on the SAN; sending the default domain information to amanagement station, the management station to configure a firstdiscovery domain including a host system selected from the list of hostsystems and an initiator selected from the list of initiators; receivingthe first discovery domain from the management station; directing themanagement server to add the first discovery domain to a list of devicedomains implemented by the management server on the SAN; and directingthe management server to enable the first discovery domain.
 18. Themethod of claim 17, further comprising: sending, from the storagedevice, a query to the management server for the default domaininformation for the SAN; wherein receiving the default domaininformation from the management server is in response to sending thequery.
 19. The method of claim 17, further comprising: receiving asecond discovery domain from the management station; directing themanagement server to add the second discovery domain to the list ofdevice domains; and directing the management server to enable the seconddiscovery domain.
 20. The method of claim 19, further comprising:directing the management server to delete the first device domain fromthe list of device domains in response to enabling the second discoverydomain.